MT Based Spoken Dialog Systems Customer/Machine Dialog

ABSTRACT

Operation of an automated dialog system is described using a source language to conduct a real time human machine dialog process with a human user using a target language. A user query in the target language is received and automatically machine translated into the source language. An automated reply of the dialog process is then delivered to the user in the target language. If the dialog process reaches an initial assistance state, a first human agent using the source language is provided to interact in real time with the user in the target language by machine translation to continue the dialog process. Then if the dialog process reaches a further assistance state, a second human agent using the target language is provided to interact in real time with the user in the target language to continue the dialog process.

TECHNICAL FIELD

The present invention relates to multi-language human-machine dialog systems.

BACKGROUND ART

It is extremely costly and time consuming to build spoken dialog systems for the same task in multiple different languages due to the required target language expertise and the data needed to build such applications. In addition, user contact centers for large corporations are often distributed across several different geographic locations to handle users that speak different languages, and any one contact center in any single country typically is not able to handle many different languages. It is, however, very costly to have all these contact centers that provide essentially the same service in different languages and in different countries.

Current state-of-the-art spoken dialog systems operate along the following path. A user calling a help desk in the United States typically will first enter a spoken dialog system (human-machine dialog) in English. In some cases there may be support for Spanish but you can't talk to the machine in Chinese, Turkish, etc. . . . in the U.S.) To talk to a human agent (human-human dialog) in the middle of the human-machine dialog, then the user will talk to an English speaking agent. If a user calls the same company's helpdesk in France, they will reach a spoken dialog system built in French, and if they decide to talk to a human agent at any point in the dialog, they will speak to an agent who speaks French.

This process means that there is a separate dialog system developed for each language for the same task and there also is a separate user contact center for each language/country. There is a huge cost associated with building the same spoken dialog system (human-machine dialog) for each language and keeping separate contact centers for each country/language.

SUMMARY

Embodiments of the present invention are directed to operation of an automated dialog system using a source language to conduct a real time human machine dialog process with a human user using a target language. A user query in the target language is received and automatically machine translated into the source language. An automated reply of the dialog process is then delivered to the user in the target language. If the dialog process reaches an initial assistance state, a first human agent using the source language is provided to interact in real time with the user in the target language by machine translation to continue the dialog process. Then if the dialog process reaches a further assistance state, a second human agent using the target language is provided to interact in real time with the user in the target language to continue the dialog process.

The dialog process may be a text dialog process or a speech dialog process or a combination of both. Delivering an automated reply may include delivering an existing dialog process reply in the target language. Delivering an automated reply also may include selecting an existing dialog process reply in the source language, performing automatic machine translation of the selected reply to the target language, and delivering the translated reply to the user.

Embodiments also include an automated dialog system using a method according to any of the above, a customer service contact center operating an automated dialog system according to any of the above, and a computer program product implemented in a computer readable storage medium for operating an automated dialog system and including program code for performing a method according to any of the above.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows functional blocks for using machine translation as a front end interface for spoken dialog systems.

FIG. 2 shows a spoke dialog system architecture for an action class process for a target language input according to an embodiment of the present invention.

DETAILED DESCRIPTION

Various embodiments of the present invention are directed to operation of a user dialog system (i.e. customer/machine, user/machine/non-native agent, user/machine/non-native agent/native agent) using automatic machine translation as an interface in the user/machine dialog. This allows one contact center in any one country to serve users from all over the world employing a single automated dialog system before sending the user call to a human agent (native or non-native). This approach is far more cost effective than the existing solutions since it eliminates the need to build the language understanding and dialog management in the target language, and instead both of these components are built only once for the source language (e.g., English). Although the following description is presented in terms of a spoken dialog system, the invention is not limited to that specific form and also would be useful in a text dialog system such as an online user service web site.

Such a dialog system is built first in a source language such as English, but is able to accept a user who speaks in a different language, for example Spanish. In one specific approach, the various target language dialog system components (e.g., Automatic Speech Recognition (ASR)/Statistical Language Model (SLM), Action Class (AC)/Understanding, Text-To-Speech (TTS)) may be developed given the corresponding elements in the source language dialog system. This can be done by translating the data using MT to the target language and building the models in the target language. Alternatively, an arrangement may be based on building only ASR and TTS in the target language and using an MT interface to perform the understanding and dialog management in the source language.

Using such arrangements, it is not necessary to build the same application in many other different languages, but instead the machine translation interface is used for routing all the customer service calls to the source language spoken dialog system. So when a customer calls in France, their speech inputs are recognized using a French ASR engine, the French text output is machine translated into English, and the English language spoken dialog system is used for the human-machine interaction. The machine dialog responses are generated/synthesized in French and the whole interaction will take place in French (at least from the customer point of view). At any point in this human-machine dialog if the customer wants to talk to a live agent, they are first forwarded to an English (source language) speaking agent in the single global contact center (assuming that speaking to an English agent is cheaper than speaking to a French agent). At this level of the dialog, the agent and the user do not speak the same language, but they communicate via machine translation of the dialog process. Each party speaks in their own language and their utterances are translated to other language. In some applications, the customer may be told they will be talking to an agent who does not speak the same language, but it may be beneficial for the customer to know that they are not talking a machine but a human. If this human-human dialog via machine translation mediation is unsuccessful, then the customer is allowed to speak to a French speaking agent.

In building a specific embodiment, the choice of the source language may be determined based on minimizing cost and the available resources. For example, English may be a typical choice of a source language because there is a large existing body of available speech and language processing tools. Another possible source language could also be Chinese because the labor employed in the single global contact center will have the lowest cost.

FIG. 1 shows various functional blocks for using machine translation as a front end interface for a spoken dialog system implemented in a source language that conducts a real time <user/machine dialog> process with a human user using a target language. A user query in the target language initially is received, step 100, and the language of the query is identified, step 101. The input speech query then can be recognized using automatic speech recognition (ASR) in the target language, step 102. The target language ASR can be built in several ways including collecting corpora (audio+text) in the target language and building acoustic and language models, or translating the text material to the target language and augmenting this data with externally retrieved data (from web or other sources) and then building a mixture of language models, or a combination of both of these methods.

Automatic machine translation is used to map the query text from the user's native target language to the system's source language in which the entire dialog system is built, step 103. To support such automatic machine translation for multiple target languages, it may be useful to build and use large parallel corpora to create generic translation tables. Task specific parallel data can be collected and task specific translation tables can be built and combined. This would allow data sharing when building MT models across many applications for anchor language and other target language pairs.

The real time <user/machine dialog> process then delivers one or more automated replies to the user in the target language, again via machine translation, step 104. If the dialog process reaches an initial assistance state, the <user/machine dialog> backs off to a hybrid <user/machine/normative-agent dialog>. In other words, a human agent using the source language is provided to interact in real time with the user in the target language by machine translation to continue the dialog process, step 105. The non-native agent can have a list of questions and answers (e.g. FAQ) to ask and/or answer to the user. The agent can simply selects the question (or answer) (text) depending on the user's response. What the non-native agent selects can be either played out from the pre-recorded audio in the target language, or it can be synthesized in the target language. Or the non-native agent can speak in the source language and a speech-to-speech translation system can translate the speech in both source and target language to enable communications. The user response is always translated to the source language for the non-native agent.

If the hybrid non-native agent dialog, step 105, then reaches a further assistance state, the process backs off to a <user/native-agent dialog> where a second human agent using the target language is provided to interact in real time with the user in the target language to continue the dialog process. The native agent may act only as a translator—and he/she may have only a minimal knowledge of the actual application. The native speaker can also be bilingual, speaking both the user's target language and the non-native agent's source language.

The technical problem becomes that of machine translation with the advantage that in the initial assistance state the previous (failed)<user/machine dialog> interaction is made available to the normative agent via MT when needed to help get an idea what the problem is and how to rapidly solve it. And similarly if the dialog reaches the further assistance state, then the previous <user/machine dialog> interaction and <user/normative-agent dialog> history are available to the native agent.

Multi-modal forms of communications (e.g., text and audio for the dialog systems) may be used between the user and the agent(s) where both <user/machine dialog> and <user/agent dialog> take place in different stages of a given dialog process. For example, if the <user/machine dialog> takes the dialog to the initial assistance state where non-native agent assistance is required, then the non-native agent joins the dialog, solves the specific problem, and hands the dialog back to the machine. The dialog can also be four-way between the user, machine, normative agent and native agent. The machine's response can be directly formulated in the target language in the form of pre-recorded audio or synthesizing generated text response in the target language (without MT), or the response (text) can be generated in the source language and gets translated to the target language via MT. Likewise, the normative agent's response can be in several ways as described above (which essentially defines a multi-modal form of interaction).

Looking more closely at the Customer/Machine/Agent Hybrid dialog, step 105, there are multiple different specific architectures that may be used for implementation of an arrangement for porting source language dialog components for use in a different target language. FIG. 2 shows an example of one specific architecture for an action classification process for a hybrid dialog process input in a given target language. The various blocks within the dashed lines may be implemented in many different specific functional variations. For example, the named entities in the dialog process may language independent where named entity class names such as STOCK-NAME & PRODUCT-NAME, their text content such as IBM, Google, & Lotus Notes, Outlook, and semantic interpretations are language independent, or not present at all. In some other cases, the named entities may be language dependent. One likely scenario that the class names and semantic interpretations are language independent, but the text content is language dependent.

The target language audio 200 initially is processed by automatic speech recognition (ASR) engine and its associated statistical language models (SLM) to produce an N-best list in the target language text, block 201. This can be using a machine translation (MT) approach that automatically translates the SLM training data to the target language preserving language independent named entities, if any, and from that the target language SLM is built. Alternatively, an MT and information-retrieval approach can be used to translate each sentence in the base language SLM training data to the target language, preserving the named entities, if any, and then for each translated SLM sentence a few sentences can be retrieved (using known information retrieval methods) from a generic target language SLM training corpus (named entities may be handled by replacing them with their contents). A generic target language SLM training corpus can be translated to the source language and retrieval carried out in the source language to benefit from improvements over single language retrieval. The target language SLM can be built based on both translated and retrieved sentences. Alternatively, a manual approach can be used to develop the ASR engine where the SLM training data is manually translated (preserving named entities) and from that the target language SLM is built. Named entities in the target language can then be tagged, block 205, using SLM training data in target language, and action class N-best hypotheses can be produced in the target language using a portion of the SLM training data or based on separate AC training data.

Looking at the left side of FIG. 2, it may be useful to modify the various source language models to best handle machine translated inputs from the target language into the source language. The target language N-best list text (from the ASR, block 201) can be machine translated to create a source language N-best list, block 202. The resulting source language N-best list text can then be tagged by a source language named entity tagger, block 203, and processed into source language action classes, block 204. At run time, the target language and source language N-best lists can be generated combined by a distribution merge process, block 207, and the combined action class hypotheses can be parsed by confirmation/disambiguation grammars for the dialog process, block 208.

The foregoing discussion treats the machine translation 202 as a black box, but in this context it may be particularly sensitive to word casing and punctuation of named entities. The named entities should be added to the dictionary of the machine translation 202 or some other means used to identify named entities which are not to be translated. Where NE class and interpretations may be language independent but the contents are language dependent, the contents should not be translated by machine translation 202 but rather external mapping or rules can be used to translate the contents. It also may be useful to use some mechanism to predict punctuations in the output of the ASR 201 to see if that improves the output of the machine translation 202.

In the case of language dependent named entities, the processes on the right side of FIG. 2 need to be ported to the target language. Specifically, the target language named entities may be ported by machine translation or manually, paying attention to pronunciations (both target language pronunciation and source language pronunciation with phone mapping) and to maintaining the source language contents. Target language ASR/SLM, named entity tagging models and action class models can be developed as previously discussed as is the left side (source language side) of FIG. 2. The action class data can also be translated manually or by machine translation to build the understanding or AC models in the target language. However, this method requires language expertise from the people who build such dialog applications. Rather than architecture such as the one in FIG. 2, some embodiments, may not necessarily need to build all the named entity models and action class models in the target language. Instead, it may be possible to build only ASR and TTS modules in the target language and use an MT interface to perform the understanding and dialog management in the source language.

An example dialog is as follows where English is the source language and Turkish as the target language. Thus, the user speaks Turkish, the non-native agent does not speak Turkish but speaks English (it can be altogether a different third language other than English and Turkish), and the native agent speaks Turkish.

U: User, M: Machine, NNA: Normative Agent, NA: Native Agent

M: Hello, how may I help you? U: Hesabimi kapatmak istiyorum [English Translation: I want to close my account]

The dialog process automatically does language identification and determines that the user is speaking in Turkish. Then the system first runs the Turkish automatic speech recognizer to transcribe the user's utterance into representative text. The transcribed utterance is sent to an TurkishEnglish machine translation (MT) system to generate the corresponding English translation given above in italics. The speech understanding component maps the translated utterance to an ACCOUNT-CLOSE action with a call-router and brings the Non-native agent (NA) into the dialog:

NNA: I am sorry to hear that, I would bring on board a native speaking agent to discuss the reasons for closing the account and see whether we can change your mind [Turkish Translation: Hesabinizi kapatmak istediginiz icin uzgunum. Simdi, sizi sizinle ayni dili konusan bir arkadasimiza baglayip, neden hesabinizi kapatmak istediginizi ogrenmek istiyoruz] [MT translates the NNA speech into Turkish] NA: Merhaba sizinle calismaya devam etmek istiyoruz, Neden hesabinizi kpatmak istiyorsunuz [English Translation: Hi, We would like to keep working with you, Why do you want to close you account?]

Embodiments of the invention may be implemented in whole or in part in any conventional computer programming language. For example, preferred embodiments may be implemented in a procedural programming language (e.g., “C”) or an object oriented programming language (e.g., “C++”, Python). Alternative embodiments of the invention may be implemented as pre-programmed hardware elements, other related components, or as a combination of hardware and software components. For example, a pseudo code representation of such an embodiment might be set forth as follows:

Process MT_Dialog receive user_query(target_language) translate user_ query(target_language, source_language) reply (user, target_language) if dialog_process = initial_assistance_state, provide source_language_agent; and if dialog_process = further_assistance_state, provide target_language_agent

Embodiments can be implemented in whole or in part as a computer program product for use with a computer system. Such implementation may include a series of computer instructions fixed either on a tangible medium, such as a computer readable medium (e.g., a diskette, CD-ROM, ROM, or fixed disk) or transmittable to a computer system, via a modem or other interface device, such as a communications adapter connected to a network over a medium. The medium may be either a tangible medium (e.g., optical or analog communications lines) or a medium implemented with wireless techniques (e.g., microwave, infrared or other transmission techniques). The series of computer instructions embodies all or part of the functionality previously described herein with respect to the system. Those skilled in the art should appreciate that such computer instructions can be written in a number of programming languages for use with many computer architectures or operating systems. Furthermore, such instructions may be stored in any memory device, such as semiconductor, magnetic, optical or other memory devices, and may be transmitted using any communications technology, such as optical, infrared, microwave, or other transmission technologies. It is expected that such a computer program product may be distributed as a removable medium with accompanying printed or electronic documentation (e.g., shrink wrapped software), preloaded with a computer system (e.g., on system ROM or fixed disk), or distributed from a server or electronic bulletin board over the network (e.g., the Internet or World Wide Web). Of course, some embodiments of the invention may be implemented as a combination of both software (e.g., a computer program product) and hardware. Still other embodiments of the invention are implemented as entirely hardware, or entirely software (e.g., a computer program product).

Although various exemplary embodiments of the invention have been disclosed, it should be apparent to those skilled in the art that various changes and modifications can be made which will achieve some of the advantages of the invention without departing from the true scope of the invention. 

What is claimed is:
 1. A method of operating an automated dialog system employing at least one hardware implemented computer processor and using a source language to conduct a real time human machine dialog process with a human user using a target language, the method comprising: receiving a user query in the target language; performing automatic machine translation of the user query into the source language; delivering an automated reply of the dialog process to the user in the target language; if the dialog process reaches an initial assistance state, providing a first human agent using the source language to interact in real time with the user in the target language by machine translation to continue the dialog process; and if the dialog process reaches a further assistance state, providing a second human agent using the target language to interact in real time with the user in the target language to continue the dialog process.
 2. A method according to claim 1, wherein delivering an automated reply includes delivering an existing dialog process reply in the target language.
 3. A method according to claim 1, wherein delivering an automated reply includes: selecting an existing dialog process reply in the source language; performing automatic machine translation of the selected reply to the target language; and delivering the translated reply to the user.
 4. A method according to claim 1, wherein the dialog process is a text dialog process.
 5. A method according to claim 1, wherein the dialog process is a speech dialog process.
 6. An automated dialog system employing at least one hardware implemented computer processor and using a source language to conduct a real time human machine dialog process with a human user using a target language, the system comprising: means for receiving a user query in the target language, means for performing automatic machine translation of the user query into the source language, and means for delivering an automated reply of the dialog process to the user in the target language; means for providing, if the dialog process reaches an initial assistance state, a first human agent using the source language to interact in real time with the user in the target language by machine translation to continue the dialog process; and means for providing, if the dialog process reaches a further assistance state, a second human agent using the target language to interact in real time with the user in the target language to continue the dialog process.
 7. A system according to claim 6, wherein the means for delivering an automated reply includes means for delivering an existing dialog process reply in the target language.
 8. A system according to claim 6, wherein the means for delivering an automated reply includes: means for selecting an existing dialog process reply in the source language; means for performing automatic machine translation of the selected reply to the target language; and means for delivering the translated reply to the user.
 9. A system according to claim 6, wherein the dialog process is a text dialog process.
 10. A system according to claim 6, wherein the dialog process is a speech dialog process.
 11. A computer program product implemented in a tangible computer readable storage medium for using a source language to conduct a real time human machine dialog process with a human user using a target language, the product comprising: program code for receiving a user query in the target language, program code for performing automatic machine translation of the user query into the source language, and program code for delivering an automated reply of the dialog process to the user in the target language; program code for providing, if the dialog process reaches an initial assistance state, a first human agent using the source language to interact in real time with the user in the target language by machine translation to continue the dialog process; and program code for providing, if the dialog process reaches a further assistance state, a second human agent using the target language to interact in real time with the user in the target language to continue the dialog process.
 12. A product according to claim 11, wherein the program code for delivering an automated reply includes program code for delivering an existing dialog process reply in the target language.
 13. A product according to claim 11, wherein the program code for delivering an automated reply includes: program code for selecting an existing dialog process reply in the source language; program code for performing automatic machine translation of the selected reply to the target language; and program code for delivering the translated reply to the user.
 14. A product according to claim 11, wherein the dialog process is a text dialog process.
 15. A product according to claim 11, wherein the dialog process is a speech dialog process.
 16. A customer service contact center operating an automated dialog system using a source language to conduct a real time human machine dialog process with a human user using a target language, the contact center comprising: a single centralized location for handling customer service inputs from remote customers using an automated dialog process including: i. receiving a user query in the target language; ii. performing automatic machine translation of the user query into the source language; iii. delivering an automated reply of the dialog process to the user in the target language; iv. if the dialog process reaches an initial assistance state, providing a first human agent using the source language to interact in real time with the user in the target language by machine translation to continue the dialog process; and v. if the dialog process reaches a further assistance state, providing a second human agent using the target language to interact in real time with the user in the target language to continue the dialog process.
 17. A customer service contact center according to claim 16, wherein delivering an automated reply includes delivering an existing dialog process reply in the target language.
 18. A customer service contact center according to claim 16, wherein delivering an automated reply includes: selecting an existing dialog process reply in the source language; performing automatic machine translation of the selected reply to the target language; and delivering the translated reply to the user.
 19. A customer service contact center according to claim 16, wherein the dialog process is a text dialog process.
 20. A customer service contact center according to claim 16, wherein the dialog process is a speech dialog process.
 21. A customer service contact center according to claim 16, wherein the source language is selected based on satisfying an objective selection function. 